Change release trigger from main push to tags#280
Conversation
@brianmhunt: Only on tagging not no any push to main?
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 14 minutes and 46 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChanged the release workflow trigger from pushes to Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/release.yml:
- Around line 15-16: The workflow currently triggers on tags matching 'v*' but
does not verify the tag equals the package version; add a validation step before
the step that runs "changeset publish" to extract the pushed tag (strip the
leading "v"), read the version from package.json (e.g., via node or npm),
compare them, and fail the job with a clear message if they differ so
accidental/mistagged tags cannot trigger a publish. Ensure the step runs after
checkout and before the publish step and references the existing tag trigger
('v*') and the "changeset publish" step so it's executed in the correct place.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e90a5c9a-403c-4618-b48e-7bded68d9b35
📒 Files selected for processing (1)
.github/workflows/release.yml
release: validate tag version before publish
|
Great catch, ty @phillipc . I added an additional check here for version-tag mismatch. |
|
@phillipc thanks for merging :) I was going to wait for the coderabbit review "just in case" I think it's good. Noting we can also tag coderabbit for review like this: @coderabbitai please re-review |
|
✅ Actions performedReview triggered.
|
@brianmhunt: Only on tagging not no any push to main?
Summary by CodeRabbit